Summary

This PR automates populating the version field in code.json from the latest GitHub release while preserving the existing merge pattern in src/main.ts.

What changed

• Removed existingCodeJSON from calculateMetaData() in src/helper.ts.
• Kept release lookup logic in the helper, but now it only returns the latest release version string.
• Moved the version fallback/merge logic into src/main.ts, following the same pattern already used for feedbackMechanism and SBOM.
• Updated unit tests in:
  • src/__tests__/unit/helper.test.ts
  • src/__tests__/unit/main.test.ts

Notes

• The implementation still uses the GitHub API release endpoint because repos.get() does not include latest release data.
• If a release version cannot be fetched, main.ts preserves the existing version from code.json.

Validation

• npx jest src/__tests__/unit/helper.test.ts src/__tests__/unit/main.test.ts

AI Usage

• Generated AI was used in this contribution

If checked, please provide an explanation on how AI was used in the development of this pull request:

• Description: Used ChatGPT (Codex) to refactor the PR to align with the existing project design patterns based on reviewer feedback.

• Type of assistance:

• Code generation

• Documentation

• Debugging

• Testing

• Refactoring

• Other:

• Scope of usage: src/main.ts, src/helper.ts, src/__tests__/unit/helper.test.ts, src/__tests__/unit/main.test.ts

• AI System used:

• ChatGPT

• Claude

• Gemini

• GitHub Copilot

• Level of modification: - [ ] As-is - [x] Modified - [ ] Used as inspiration

• Prompts used: "Please refactor my code to address reviewer feedback on my PR... revert the function signature in helper.ts, move the merging logic to main.ts, and update the corresponding unit tests."